∂11-Dec-78  2340	Feinler at SRI-KL (Jake Feinler) 	ATTN: Technical Liaison  RE: Duties and Responsibilities
Date: 11 Dec 1978 2247-PST
From: Feinler at SRI-KL (Jake Feinler)
Subject: ATTN: Technical Liaison  RE: Duties and Responsibilities
To:   [SRI-KL]<NETINFO>LIAISON-12-78:

The following outlines the duties and responsibilities of the ARPANET
Technical Liaison.  This document was prepared jointly by the NIC and DCA
Code 535 and was then presented to the ARPANET Sponsors.  It is being sent 
for your information and in response to a request from many of you for such
a document.

------------

                               HOST/TIP
                       ARPANET TECHNICAL LIAISON

The ARPANET Technical Liaison act as advisors to network users, the 
Network Information Center (NIC), the Network Control Center (NCC), and 
the Defense Communications Agency (DCA) on technical matters relating to
the ARPANET.  The Liaison are the chief source of information about 
individual ARPANET hosts.  They often contribute to the design of 
network protocols and related software and make suggestions for needed 
changes and improvements through memos, RFCs (network technical notes), 
and participation in network working groups.  The work they do is on a 
volunteer basis, and they are in themselves a valuable network resource.

The Liaison are traditionally individuals trained in computer science or
a related field, and are familiar with the resources available at the 
host they represent.  Each host on the network has no more than one 
Technical Liaison; however, the same person may serve as liaison for 
more than one host.  The Technical Liaison are coordinated by the 
Manager of the ARPANET Network Information Center, currently Elizabeth 
Feinler (FEINLER@SRI-KL).

LIAISON DUTIES AND RESPONSIBILITIES:

1.  Help monitor the ARPANET from unauthorized use.  Permission to 
attach hosts or other equipment to the ARPANET can only be granted by a 
sponsoring agency.  The Liaison should refer all requests for such 
attachments to DCA.  Permission to use existing host resources can only 
be granted by authorized host administrators to users with valid 
accounts.  The Liaison should refer all requests for such access to the 
proper administrators.  If it is possible to gain access to the ARPANET 
from a tributary terminal off a host via the IMP-HOST connection, it is 
the responsibility of that host to prevent illegal use.  Distribution of
TIP dial-in numbers is entrusted to the TIP Liaison.  Evidence of 
unauthorized use of these numbers should be reported to DCA.

2.  Upon completion of new host or terminal hardware installation and 
prior to the new user passing traffic, the Liaison must contact DCA Code
535 via telephone or ARPANET for final validation.  DCA will then 
instruct BBN to set the host/terminal parameters to accept traffic.  The
Liaison should also provide the NIC via telephone or ARPANET with his 
full name, address, phone number, and network mailbox (if this has not 
already been done), as well as the host name, host address, operating 
system, and computer configuration for any new hosts.

3.  Help coordinate equipment moves or installations, or circuit moves 
or installations affecting the ARPANET backbone or the IMPs and/or TIPS.
The Liaison will be sent info copies of Telecommunications Service 
Requests (TSR's) from DCA, informing them of any changes in backbone 
circuitry, terminal and/or host additions/deletions.  They should help 
coordinate access to the IMP or TIP by TEL CO or BBN to perform actions 
called for in the TSRs.  Unless a TSR has been received authorizing 
equipment moves/installations or circuit moves/additions, no such moves 
or installations should be made without contacting DCA Code 535 for 
authorization.  (Normal maintenance actions are excluded.)

4.  TIP Liaison are required to forward to DCA Code 535 a quarterly TIP 
inventory in format attached (RCS #DCA(Q)530-49).  The inventory is due 
by the 15th of January, April, July, and October of each year.  
Transmission via ARPANET is acceptable.

5.  In the first five working days of each month the NIC will provide 
via the ARPANET, a table of ARPANET Host Names, Liaison, and Sponsors. 
Liaison should review entries on this list pertaining to their TIPs or 
Hosts for accuracy and provide changes as soon as possible to the NIC.

6.  Provide the NIC with a description of equipment, software, people, 
and interests pertaining to their designated hosts in accordance with 
the formats outlined by the NIC.

7.  Provide the NIC with updated personnel information for the ARPANET 
Directory and online Identification Data Base.

8.  Keep local users informed about procedures and happenings related to
the ARPANET.  The Liaison will be the recipient of official messages 
sent out about the ARPANET.  These messages should be 'posted' and/or 
passed on to local users, administrators, or other interested personnel.

9.  Serve as local contact for their host(s).  If an ARPANET user does 
not know how to locate a particular resource, or how to handle a problem
at the host level, and does not know who to contact, he can ask the 
Network Liaison at the host he is trying to use to assist him.  The 
Liaison can either help him directly or refer him to the proper contact.

10.  Inform the NCC and DCA of network backbone problems and network 
software bugs, and generate Unsatisfactory Service Reports as necessary.
See that ARPANET protocols are implemented properly at the host level.  
(This activity may be delegated if the Liaison is not the maintainer of 
the network software.  However, the Liaison is expected to be the 
contact for protocol information distributed to the hosts and to see 
that the right person receives it.)

11.  Contacts

   DCA Code 535
     Telephone:  (202) 692-6175/6176
     AUTOVON:    222-6175/6176
     ARPANET:    DCACODE535@USC-ISI

   Network Information Center (NIC)
     Telephone:  (415) 326-6200 ext 3695
     ARPANET:    FEINLER@SRI-KL

   BBN Network Control Center (NCC)
     Telephone:  (617) 661-0100
     ARPANET:    POWERS@BBN-TENEXE
   
   
   

  

                   QUARTERLY TIP INVENTORY
                    (RCS# DCA(Q) 530-49)

TIP Name                                         Date
        ------------------------------               -------------

           TYPE (BAUD RATE)                            User (if leased)
           D-Dial   L-Leased      Modem                Sponsor (if
MLC Port   R-Room    Circuit      Mfgr. & Model #        dial-up)

   1

   2

   3

   4

   5

   6

   .

   .

   .

   63



Signed                                             (TIP Liaison)
      --------------------------------------------

-------